feat: add skipCi option
#264
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Can customize the way the "skip ci" information is passed to git
|
Hello, is there someone here ? @pvdlg are you still here ? |
|
I'm a big fan of this... hopefully it can be reviewed. |
|
Thanks, but I'm starting to lose hope |
|
@travi is this something that you'd be interested in? It looks like a great way to clean up the release message. |
|
Big fan of this feature. Any update ? |
|
@travi If you are interested I could probably rework this in a |
|
Anyone from @semantic-release interested in helping moving this feature forward? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR add the ability to plugin's user to specify the way he wants to pass the "skip ci" information.
By default, the
[skip ci]keyword is passed to the commit message, but this behavior is not always the required one. Worse, it is hard fixed to the default commit message, and the plugin's user have to copy/paste the default commit message omitting this keyword if he doesn't want it.This option permit to specify
messagevalue to keep the default behavior,pushOptionvalue to use the git "push-option" functionnality (a warning is raised in README about git version compliance) orfalseto simply remove the keyword in default message.It answsers to a (already closed) issue #171.
Like I said in this issue, I'm not a really good english speaker/writer, so forgive my comment and please review my
READMEupdates. 😅Another thing, it is my very first contribution/PR on github, I hope I correctly follow the process 🙂